Transactions associated with a mobile device

ABSTRACT

Methods and apparatus, including computer program products, for transactions associated with a mobile device. A method includes, in a merchant device linked to a server by a first network, sending a registration to the server, sending a transaction message to the server, receiving a unique identifier from the server in response to the transaction message, broadcasting the unique identifier, in response to the broadcasted unique identifier, receiving instructions in the server from a mobile application residing in a memory of a mobile device over a second network, processing a transaction in response to the instructions, and notifying the merchant device of the processed transaction.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.61/295,490. filed Jan. 15, 2010. and titled A SYSTEM FOR RAPID PAYMENTUSING A MOBILE DEVICE, which is incorporated by reference in itsentirety.

BACKGROUND OF THE INVENTION

The present invention relates to mobile devices and data processing bydigital computer, and more particularly to transactions associated witha mobile device.

Advances in processor, memory, and wireless technologies have led to theproliferation of mobile electronic devices. Typical mobile devices, suchas WiFi-enabled wireless mobile phones (e.g., WiFi-enabled smartphones)and personal digital assistants (WiFi-enabled PDAs) provide a wide arrayof services, such as cellular calling, email, text messaging, calendarand address book services, media object acquisition and playbackservices, and camera services, among many others. In acquiring mediaobjects, cell phone minutes, or other goods or services available overthe Internet, mobile devices often provide users with the samefunctionalities as other computing devices.

Concurrently, merchants such as retailers, wholesalers, and serviceproviders offer customers a wide variety of payment methods. Customerscan often pay via any of cash, check, money order, gift card, creditcard, and debit card. The variety of payment methods, combined with thefact that many merchants do not accept certain types of credit cards,and so forth, requires customers to carry on their persons instrumentsassociated with a large number of payment methods (e.g. credit cards,debit cards). Carrying this wide array of payment method instruments isoften quite burdensome to many customers.

SUMMARY OF THE INVENTION

The present invention provides methods and apparatus, including computerprogram products, for transactions associated with a mobile device.

In general, in one aspect, the invention features a method including, ina merchant device linked to a server by a first network, sending aregistration to the server, sending a transaction message to the server,receiving a unique identifier from the server in response to thetransaction message, broadcasting the unique identifier, in response tothe broadcasted unique identifier, receiving instructions in the serverfrom a mobile application residing in a memory of a mobile device over asecond network, processing a transaction in response to theinstructions, and notifying the merchant device of the processedtransaction.

In another aspect, the invention features a method including, in amobile device having a mobile application residing in a memory,detecting a unique identifier broadcasted by a merchant device over afirst network, sending a transaction message containing the uniqueidentifier over a second network to a server, receiving a transactionsummary from the server over the second network, and sending processinginstructions to the server over the second network in response to thereceived transaction summary.

Other features and advantages of the invention are apparent from thefollowing description, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be more fully understood by reference to the detaileddescription, in conjunction with the following figures, wherein:

FIG. 1 is a block diagram.

FIG. 2 is a block diagram.

FIG. 3 is a flow diagram.

FIG. 4 is a flow diagram.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

Illustrative embodiments of the present invention include, but are notlimited to, methods and apparatuses for a service provider capable ofproviding transactional services to a mobile device user for one or moretransactions with a merchant providing goods and/or services.

As shown in FIG. 1, a system 10 includes a merchant device 12 connectedto merchant point of sale (POS) system 14. Although the exemplary system10 shows the merchant device 12 linked to the merchant POS system 14,other implementations are possible. For example, in one implementation,the merchant device 12 can be linked to a merchant datacenter thatprocesses all transactions. The merchant device 12 is linked to a server16 by a network 18. The system 10 also includes a mobile device 20linked by a network 22 to the server 16. The network 18 can be wired orwireless. The network 22 is a wireless network (e.g., IEEE 802.11.Bluetooth). The server 16 is linked to one or more financial servers 23.The financial servers 23 provide secured transactions, such ascredit/debit card transactions, and information related to thesefinancial transactions. In other implementations, secured transactionsare performed internally by a merchant datacenter.

In general, a POS system, such as POS system 14, is a computerizedreplacement for a cash register. Much more complex than the cashregisters of even just a few years ago, the POS system can include anability to record and track customer orders, process credit and debitcards, connect to other systems in a network, and manage inventory.Generally, the POS system has as its core a personal computer, which isprovided with application-specific programs and input/output (I/O)devices for the particular environment in which it will serve.

The merchant device 12 is a hardware device containing software thatcommunicates transaction information over the network 18 from themerchant POS system 14 to the server 16. In one specific example, themerchant device 12 communicates transaction information over the network18 in coordination with information transmitted by the POS system 14.

The mobile device 20 can be a personal digital assistant (PDA),enterprise digital assistant or mobile phone, such as an Apple® iPhone®,Blackberry® or Android™ phone. The mobile device 20 includes a clientapplication 100 residing in a memory 24. In one specific example, theclient application 100, also referred to as mobile application 100, isdownloaded by a mobile device user from an app store or other mobilesoftware distribution platform.

The merchant device 12 provides an indication to the mobile device 20through the client application 100 that transactions with the merchantdevice 12 are available. The indication may include audio and/or videoindication. More particularly, the merchant device 12 is represented bya unique identifier. In one example, the unique identifier is a 48-bitMedia Access Control (MAC) address, with the first three octets of48-bit MAC address referred to as an Organizationally Unique Identifier(OUI) assigned by the Institute of Electrical and Electronics Engineers(IEEE). In this example, the 48-bit number is used as a Basic ServiceSet Identifier (BSSID) for network 22. Transactions include the purchaseof goods and/or services offered by a merchant having the merchantdevice 12.

Other merchant device configurations are possible, depending on theequipment available at the merchant site. In one example, the merchantdevice 12 includes a display screen, a wireless local area network(WLAN) device based on the IEEE 802.11 (e.g., WiFi), and a facility forinternet connectivity. The merchant device 12 may connect to a POSterminal.

In another example, a display device is external to the merchant device12. Internet connectivity can use an existing merchant internetconnection or the merchant device 12 can have a “self-contained”Internet connection using a wide area network (WAN) such as Generalpacket radio service (GPRS). In still another example, the merchantdevice 12 can connect to a personal computer and/or mobile phone thatenables both a display and Internet access to the merchant device 12.

In another example, the merchant device 12 is a mobile phone such as anApple® iPhone® or Android® phone that has the ability to transmit WiFipackets and connect to the internet by itself. In still another example,the merchant device 12 may not include a display device and simplyinterface to, or be included with, existing merchant payment systems,such as, for example, card swipe terminals or point of sale systems.

The mobile device 20 is capable of connecting to a WAN, typically theInternet, in order to contact the server 16. The mobile device 20detects broadcasts by the merchant device 12. Typically, thesebroadcasts advertise an availability of networks using a technology suchas IEEE 802.11 Wireless Networking or Bluetooth Wireless Networking. Ina specific example, the mobile device 20 resides in an automobile havingan advanced control system, such as the Ford® SYNC from Ford MotorCorporation, which provides WiFi, an ability to run applicationsdesigned by third parties and connection to the Internet.

As described above, the mobile device 20 includes the client application100. Client application 100 is a process that executes in the mobiledevice 20, detects a presence of the merchant device 12 and communicatesthe detected merchant and additional information to the server 16. Theclient application 100 provides a visual interface to the user enablingthe user to perform a variety of tasks, including reviewing transactiondetails, approving payment, correcting payment problems, and providingidentification (such as a password or other biometric identification) toprove an identity of the user. In embodiments, the client application100 performs a variety of other tasks, such as keeping electronicreceipts of purchases made by the user from the merchant, enablingmultiple parties to coordinate payment (e.g., ten of a party oftwenty-three splitting a restaurant bill), and/or displaying specialoffers from the merchant or related merchants either before or after apayment transaction has occurred.

As shown in FIG. 2, the server 16 is a computer or set of computers madeavailable on networks 18, 22 to enable access by the merchant device 12and the client application 100 residing in the mobile device 20. Theserver 16 can include a processor 26, memory 28, an input/output (I/O)device 30 displaying a user interface (UI) 32 and a service interface 34for communicating with other entities in the networks 18, 22. The server16 also includes a database 36 residing in the memory 28 or in anexternal storage device (not shown). The database 36 serves as a storeof information, such as merchant information, customer information,transaction information, configuration information, historicalinformation and so forth. The server 16 includes a payment networkinterface 38 for processing transactions with the financial server(s)23.

Payments flow through the server 16 by communication with the clientapplication 100 or the merchant device 12. Communication between themerchant device 12 and the server 16 takes place through the serviceinterface 34. Communication between customers or merchants and theserver 16 takes place through the UI 32.

The server 16 can provide significantly expanded configuration andsetting information to the merchant, such as couponing, frequent userprograms, and/or an ability to gather contact information frompurchasers on an opt-in (i.e., voluntary) basis.

The merchant device 12 may interface directly with a variety of otherdevices resident or in proximity to the merchant's physical location.These other devices can include devices selected from the groupincluding cash registers, credit/debit card terminals, point of salesystems, display terminals, receipt printers and networking equipmentsuch as a router or hub.

Prior to enabling payments, a merchant establishes a network connectionto the merchant device 12 and registers with the server 16. Registrationinformation includes information necessary to process a paymenttransaction on his or her behalf. Once registration is complete, theserver 16 associates the merchant device's unique identifier withmerchant account information.

Prior to a customer's first transaction, the customer registers with theserver 16. This registration can be implemented within the clientapplication 100 or from any other device capable of accessing the server16 over a network, such as a laptop/notebook computer or a personalcomputer (PC). During customer registration, the customer providespayment information suitable for making purchases. This information isstored by the server 16.

Information collected and stored in the records may be modest orextensive, depending upon the variety of transactions the registrantdesires to engage in. Basic personal information, such as name, address,email address, and phone number may be collected, as well as informationassociated with the mobile device 20 to be associated with theregistration, such as wireless service provider, wireless accountnumber, communication features of the phone (email, SMS, and so forth),and a mobile device 20 phone number. In addition, payment methods thatthe registrant wishes to use, such as debit and credit card accounts,may be provided along with the relevant name(s) on the account, theaccount numbers, card expiration dates, and names of the financialinstitutions associated with the payment method accounts may also becollected. Further, information about service features associated withthe mobile device 20, such as cellular minutes, text messages, and mediaobject downloads may be collected and stored. Other information may alsobe collected and stored. Thus, the above recitation is in no wayintended to fully set forth all collected and stored data.

Once the merchant device 12 is registered with the server 16, themerchant device 12 broadcasts its availability. Mobile devices who haveregistered with the server 16, such as mobile device 20, and are withinrange of the merchant device's broadcast, detect the broadcast.Broadcast detection is enabled by the client application 100. Detectionof the broadcast enables the user of the mobile device 20 to conducttransactions through the server 16 with the merchant having the merchantdevice 12. Communication of the merchant device 12 with the server 16 isindependent from communication of the mobile device 20 with the server16.

Transactions can include purchasing goods and services offered by themerchant and/or payment of purchased goods and/or services of themerchant.

Interactions among the elements in system 10 are described more fully asfollows. As described above, system 10 includes a physical device usedby the merchant (i.e., merchant device 12), the client application 100used by the customer on the mobile device 20, and the server 16supporting both payment processing and communication between the clientapplication 100 and the merchant device 12. A goal is to provideverifiable payment information such that a transaction can be completedquickly—typically as quickly as a normal credit card transaction using amodern electronic credit card reader system. At the time of an exemplarypurchase, the following steps complete a transaction. Certain elementsmay occur in different order as there are essentially two independentactors—the merchant and the customer (user). For simplicity, anexemplary flow presented below illustrates the merchant acting first. Inother instances, the user may begin before the merchant, waiting for therelevant action from the Merchant to complete a transaction.

By way of example, a customer may desire to pay for an item or service.The merchant starts by sending an amount and optionally otherinformation, such as line item details, to the merchant device 12. Themerchant device 12 sends a message to the server 16 that it is preparedto charge the particular amount. This message includes the merchantaccount information and device identifier, as well as other informationprovided to the merchant device 12 in the context of the transaction.For example, the message may include details of how the amount may bechanged (e.g., additional tip amount). For another example, the messagemay contain line item details including products purchased, taxableamounts and/or other service charges.

The server 16 stores or caches the information sent by the merchantdevice 12 and returns an identifier, which may or may not be globallyunique, merchant unique, or customer unique, to the merchant device 12.The merchant device 12 begins broadcasting its unique identifier (e.g. aBSSID over its WiFi) or an identifier derived from its uniqueidentifier, using a technology such as IEEE 802. Wireless Networking orBluetooth, that the mobile device 12 can detect; at approximately thesame time, if a customer-facing screen is present, the signal maydisplay an instruction to the customer to initiate the transaction,which may include a “reference number” to disambiguate simultaneoustransactions at a merchant. The user launches (or is already running)the client application 100 and may optionally be required to providevalidation credentials, such as a password or “identifying gesture,”such as a finger swipe, fingerprint, or other biometric identification.The client application 100 detects relevant wireless networks (e.g.,filtering the BSSID by a predetermined OUI prefix or by filtering basedon the “name” or SSID 24 of the discovered networks).

The client application 100 sends a request to the server 16 asking forinformation about the current transaction being proffered by themerchant device 12 in range as represented by the unique identifier ofthe device. Should there be multiple candidate transactions in range ofthe same set of merchant devices, various disambiguation strategies maybe used. For example, the customer may be asked to type in the amount ofthe transaction, or a sales register number, or any other piece ofinformation which differentiates one merchant device from another. Inanother instance, a signal strength of the available merchant device maybe used to triangulate position or simply choose the highest powermerchant device.

The server 16 sends the client application 100 information about thepurchase. The user views the information displayed by the clientapplication 100, and if satisfied, that the correct amount is beingcharged or the products are as expected, and confirms the transaction.Confirmation may include a simple button press or require a signature orother identifying device (e.g., biometrics, fingerprints, and so forth).

As discussed supra, alterations to the order may be made, such as tipamount. Other alterations to the order or amount may proceed prior tothe completion of the transaction. For example, the merchant or customermay desire to remove an item from the transaction and update the amountand/or line item details. Upon customer confirmation, the clientapplication 100 sends a confirmation message to the Server 16. TheServer 16 processes the customer's payment information, typically acredit card transaction. In one instance, the “merchant identifier,” anumber given out by the credit card processor to the merchant, may beused. In another instance, a merchant identifier held by the entityoperating the overall system may be used to serve multiple merchants,like Paypal®, Google® Checkout and so forth. The server 16 informs themerchant device 12 that the transaction was successful, which theneither displays this information to the merchant, or informs a Point ofSale system that the transaction was successful. The server 16 informsthe client application that the transaction was successful.

Other embodiments are within the scope of the invention described above.Elements of the system 10 can be used outside the scope of a financialtransaction. For example, if a customer sees a window sticker at amerchant location that advertises support of the system 10, the customermay start the client application 100 and be apprised of special offersavailable at the merchant. This includes client application 100detecting relevant broadcast unique identifiers, sending them to theserver 16, and getting special offers from the merchant or relatedmerchants potentially customized to the individual and/or their previousbuying habits with the merchant or other merchants.

In other embodiments, functionality in a restaurant, a menu may enableordering directly on the mobile phone; at a gas station, a specializedinterface for specifying fuel grade and maximum amount may be presentedto the user. The system 10 can also be used to implement coupons orloyalty card programs. In concert with a financial transaction, a“virtual” loyalty card may receive value as a result of a transaction,and that value may be redeemed using the system 10 at that point or inthe future.

In certain situations, such as group dining, multiple customers maydesire to participate in a single transaction. If an active transactionexists for one or more customers and one or more additional customerswish to participate in payment (and if the merchant has enabled thistransaction to be paid by multiple parties), the other customers canstart the client application 100 on their respective mobile devices. Theclient applications detect the merchant device and request to enroll inthe appropriate transaction. One or more customers having alreadycompleted a transaction may be prompted to approve the new paying party.The client applications of the existing customers and/or additionalparticipating customers presents an interface enabling the respectiveparties to determine how the payment will be divided. After this hasbeen determined, each customer can complete payment and the merchantdevice is notified of the outcome.

In another embodiment, the merchant device 12 broadcasts an availabilityof a network using the BSSID as the unique identifier of the merchantdevice 12. In a specific example, the merchant device 12 broadcasts morethan one BSSID over the course of a transaction. In cooperation with theserver 16, this enables the merchant device 12 to indicate certaininformation by manipulating a secondary BSSID. For example, thesecondary BSSID can indicate a price of an available transaction. Usingthe secondary BSSID enables efficient communication of several keyfacts, for example, that the merchant device 12 in question is currentlyoffering a transaction, and/or the price of that transaction obscured bya key that is only known to the merchant device 12 and the clientapplication 100 (which prevents unrelated parties from snooping).

In one embodiment, an act of the client application 100 sendingdiscovered unique identifiers to the server 16 enables the server 16 topresent “candidate payers” to the merchant device 12 (e.g., presenting aphoto of the person). This in turn enables a merchant operator to makesure they are charging the right person in a high-capacity checkoutsituation having cash registers in close physical proximity to oneanother.

In another embodiment, if the mobile device 20 cannot contact the server16 on its own Internet connection, the merchant device may act as a“traditional” wireless access point (WAP) and offer to route informationfrom the mobile device 20 to the server 16. Since communications betweenthe mobile device 20 and server 16 accommodate third party “observers,”this arrangement presents no security challenges; the identity andsecurity mechanisms used to connect to the merchant device 12 may bedependent on which particular mobile device 20 is in use (for example,the username and password for the access point may be related to theuser of the mobile device 20).

As shown in FIG. 3, the process 100 includes, in a mobile device havinga mobile application residing in a memory, detecting (102) a uniqueidentifier broadcasted by a merchant device over a first network. Themobile device can be a WiFi-enabled wireless mobile phone, WiFi-enabledpersonal data assistant (PDA) or mobile device residing in an automobilehaving advanced control system. The unique identifier can be a MediaAccess Control (MAC) address of the merchant device.

Process 100 sends (104) a transaction message containing the uniqueidentifier over a second network to a server. The server can be linkedto a financial processing server over a third network. The financialprocessing server can be a credit card/debit card transaction server.

Process 100 receives (106) a transaction summary from the server overthe second network. The transaction summary can include transactiondetails for the purchase or sale of goods or services, including price.

Process 100 sends (108) processing instructions to the server over thesecond network in response to the received transaction summary.

Process 100 receives (110) transaction confirmation from the server.

As shown in FIG. 4, a merchant device process 200 includes, in amerchant device linked to a server by a first network, sending (202) aregistration to the server. The registration may include informationrelated to the merchant device. The merchant device can be linked to apoint of sale (POS) system.

The server can be linked to a financial processing server over a thirdnetwork. The financial processing server can be a credit card/debit cardtransaction server.

Process 200 sends (204) a transaction message to the server. Thetransaction message can include transaction details for the purchase orsale of goods or services, including price.

Process 200 receives (206) a unique identifier from the server inresponse to the transaction message. The unique identifier can be aMedia Access Control (MAC) address of the merchant device.

Process 200 broadcasts (208) the unique identifier.

Process 200, in response to the broadcasted unique identifier, receives(210) instructions in the server from a mobile application residing in amemory of a mobile device over a second network. The second network canbe a wireless network. The instructions can be payment instructions.

The mobile device can be a WiFi-enabled wireless mobile phone,WiFi-enabled personal data assistant (PDA), or a mobile device residingin an automobile having an advanced control system.

Process 200 processes (212) a transaction in response to theinstructions. The transaction may be processed by the server. Thetransaction may be processed by the merchant device in response toreceiving the instructions from the server.

Process 200 notifies (214) the merchant device of the processedtransaction.

Process 200 notifies (216) the mobile application of the processedtransaction.

Embodiments of the invention can be implemented in digital electroniccircuitry, or in computer hardware, firmware, software, or incombinations of them. Embodiments of the invention can be implemented asa computer program product, i.e., a computer program tangibly embodiedin an information carrier, e.g., in a machine readable storage device orin a propagated signal, for execution by, or to control the operationof, data processing apparatus, e.g., a programmable processor, acomputer, or multiple computers. A computer program can be written inany form of programming language, including compiled or interpretedlanguages, and it can be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unitsuitable for use in a computing environment. A computer program can bedeployed to be executed on one computer or on multiple computers at onesite or distributed across multiple sites and interconnected by acommunication network.

Method steps of embodiments of the invention can be performed by one ormore programmable processors executing a computer program to performfunctions of the invention by operating on input data and generatingoutput. Method steps can also be performed by, and apparatus of theinvention can be implemented as, special purpose logic circuitry, e.g.,an FPGA (field programmable gate array) or an ASIC (application specificintegrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read only memory ora random access memory or both. The essential elements of a computer area processor for executing instructions and one or more memory devicesfor storing instructions and data. Generally, a computer will alsoinclude, or be operatively coupled to receive data from or transfer datato, or both, one or more mass storage devices for storing data, e.g.,magnetic, magneto optical disks, or optical disks. Information carrierssuitable for embodying computer program instructions and data includeall forms of non volatile memory, including by way of examplesemiconductor memory devices, e.g., EPROM, EEPROM, and flash memorydevices; magnetic disks, e.g., internal hard disks or removable disks;magneto optical disks; and CD ROM and DVD-ROM disks. The processor andthe memory can be supplemented by, or incorporated in special purposelogic circuitry.

It is to be understood that the foregoing description is intended toillustrate and not to limit the scope of the invention, which is definedby the scope of the appended claims. Other embodiments are within thescope of the following claims.

What is claimed is:
 1. A method comprising: in a merchant device linkedto a server by a first network, sending a registration to the server;sending a transaction message to the server; receiving, on the merchantdevice, a unique identifier from the server in response to thetransaction message; broadcasting, from the merchant device, the uniqueidentifier to enable a mobile device to detect the unique identifier; inresponse to the broadcasted unique identifier, receiving instructions inthe server from a mobile application residing in a memory of a mobiledevice over a second network; processing a transaction in response tothe instructions; and notifying the merchant device of the processedtransaction.
 2. The method of claim 1 wherein the transaction isprocessed by the server.
 3. The method of claim 1 wherein thetransaction is processed by the merchant device in response to receivingthe instructions from the server.
 4. The method of claim 1 furthercomprising notifying the mobile application of the processedtransaction.
 5. The method of claim 1 wherein the registration comprisesinformation related to the merchant device.
 6. The method of claim 1wherein the merchant device is linked to a point of sale (POS) system.7. The method of claim 1 wherein the transaction message comprisestransaction details for the purchase or sale of goods or services,including price.
 8. The method of claim 1 wherein the unique identifieris a Media Access Control (MAC) address of the merchant device.
 9. Themethod of claim 1 wherein the second network is a wireless network. 10.The method of claim 1 wherein the instructions are payment instructions.11. The method of claim 1 further comprising receiving a confirmation ofthe processed transaction from the server.
 12. The method of claim 1wherein the server is linked to a financial processing server over athird network.
 13. The method of claim 12 wherein the financialprocessing server is a credit card/debit card transaction server. 14.The method of claim 1 wherein the mobile device is selected from thegroup consisting of WiFi-enabled wireless mobile phones, WiFi-enabledpersonal data assistants (PDAs) and mobile devices residing in anautomobile having advanced control systems.
 15. A method comprising: ina mobile device having a mobile application residing in a memory,detecting a unique identifier broadcasted by a merchant device over afirst network, the unique identifier generated by a server in responseto a communication from the merchant device; sending a transactionmessage containing the unique identifier over a second network to theserver; receiving a transaction summary from the server over the secondnetwork; and sending processing instructions to the server over thesecond network in response to the received transaction summary.
 16. Themethod of claim 15 wherein the mobile device is selected from the groupconsisting of WiFi-enabled wireless mobile phones, WiFi-enabled personaldata assistants (PDAs) and mobile devices residing in an automobilehaving advanced control systems.
 17. The method of claim 15 wherein theunique identifier is a Media Access Control (MAC) address of themerchant device.
 18. The method of claim 15 wherein the transactionsummary comprises transaction details for the purchase or sale of goodsor services, including price.
 19. The method of claim 15 wherein theprocessing instructions comprise credit card or debit card information.20. The method of claim 15 further comprising receiving transactionconfirmation from the server.
 21. The method of claim 15 wherein theserver is linked to a financial processing server over a third network.22. The method of claim 21 wherein the financial processing server is acredit card/debit card transaction server.